Residential gateway making at least one private memory space available

ABSTRACT

A residential gateway ( 110 ) has a memory space ( 132 ), with at least one private memory space ( 130 ), made available to at least one device ( 111; 112 ) connected to a local area network ( 120 ). The residential gateway has a table ( 140 ) managing rights of access to the private memory space or spaces; a device for receiving commands for access to the memory space and administrator commands for updating the access rights management table; a device for updating the table, on receipt of an administrator command coming from a predetermined device implementing an administrator module, and for ignoring any administrator command coming from another device; and a device ( 150 ) for ignoring any command for access to the private memory space or spaces, when the command is received coming from a device not identified in the table.

This application is the U.S. national phase of International ApplicationNo. PCT/EP2014/067275 filed 12 Aug. 2014 which designated the U.S. andclaims priority to FR Patent Application No. 13/58115 filed 22 Aug.2013, the entire contents of each of which are hereby incorporated byreference.

The present invention relates to a residential gateway intended to beconnected to a local area network and having available a memory spaceintended to be made available to at least one device connected to thelocal area network.

At the present time, many devices in a residential communication networkincorporate hard disc drives. In particular hard disc drives are foundincorporated in STB (Set Top Box) decoding devices and in residentialgateways. A hard disc drive installed in a residential gateway typicallyimplements NAS (Networked Attached Storage) network disc drive functionsthus offering public memory space available to other devices connectedto the residential communication network. A hard disc drive installed inan STB decoding device typically implements PVR (Personal VideoRecorder) video recording functions and/or time shifting functions, thusoffering a private memory space accessible only to the innards of theSTB decoding device, in order to prevent a user recovering and makingavailable via the Internet any audiovisual content recorded on the harddisc drive.

It is desirable to enable pooling these various uses of memory space inthe same disc drive or group of disc drives, while complying with theconstraint of public and private accessibility inherent in these uses.

It is also desirable to allow such pooling, while meeting a constraintof latency of access to the hard disc drive in the context of recordingsand readings of audiovisual data, as is the case in the implementationof PVR video recording and time shifting functions.

It is in particular desirable to provide a solution that is simple toimplement at low cost.

The invention relates to a residential gateway intended to be connectedto a local area network, the residential gateway having a memory spaceintended to be made available to at least one device connected to thelocal area network. Said memory space comprising at least one privatememory space, the residential gateway is such that it comprises: a tablemanaging rights of access to said private memory space or spaces; meansfor receiving commands for access to said memory space and administratorcommands for updating said access rights management table; means forupdating said access rights management table, on receipt of anadministrator command coming from a predetermined device implementing anadministrator module, and for ignoring any administrator command comingfrom a device not implementing said administrator module; means forignoring any command for access to said private memory space or spaces,when said command is received coming from a device not identified insaid access rights management table. Thus, by implementing such a tablemanaging rights of access to said private memory space or spaces andensuring that only the administrator module or modules known to theresidential gateway is or are in a position to modify this table, theaforementioned accessibility rules can be complied with, while enablingpooling the location of the memory spaces in the local area network.This enables in particular moving a hard disc drive normallyincorporated in an STB decoding device to the residential gateway. Sincethe residential gateway is a device intended by nature to be permanentlyswitched on, the STB decoding device can have access thereto wheneverrequired, and no problem of energy regulation is posed, which would nothave been the case by moving the hard disc drive from the residentialgateway to the STB decoding device.

According to a particular embodiment, the residential gateway is adaptedfor receiving, via the local area network, said commands for access tosaid memory space in the form of link layer messages. Thus the latencyin transmission and processing of these commands is significantlyreduced compared with accesses by network or transport layer messages ofthe OSI (Open Systems Interconnection) model. In addition, since theprocessing operations are fewer, a processor with a lower performancecan be used in the residential gateway.

According to a particular embodiment, the residential gateway is adaptedfor receiving, via the local area network, said commands for access tosaid memory space in the form of messages in accordance with the AoEprotocol (ATA over Ethernet, ATA being the acronym for AdvancedTechnology Attachment). Thus implementation remains simple andcompatible with off-the-shelf legacy devices.

According to a particular embodiment, the residential gateway comprisesmeans for ignoring any command of the “MAC Mask List” type concerningsaid private memory space or spaces.

According to a particular embodiment, the residential gateway comprisesa server for each private memory space, each server being adapted forfiltering and processing the commands for access to said private memoryspace, and means for broadcasting a message describing the configurationof each server, said message including a description of the privatememory space managed by said server.

According to a particular embodiment, the memory space furthercomprising at least one public memory space not taken into account bythe access rights management table, the residential gateway comprises aserver for each public memory space, the residential gateway comprises aqueue in which each server managing a private or public memory spaceplaces commands for access to the memory space to be executed. Thusmanaging competing accesses to the same medium is simplified.

According to a particular embodiment, each server is associated with apriority level and each command for access to the memory space is placedin the queue according to the priority level associated with the serversupplying said command to be executed. Thus it is possible to favourcertain accesses compared with others, in order better to respond tolatency constraints. For example, it is thus possible to execute as apriority accesses to the memory space for video applications of the PVRor time shifting type.

According to a particular embodiment, when the residential gateway isnot the device implementing the administrator module, the residentialgateway implements means for pairing the residential gateway with thedevice implementing the administrator module. Thus configuration issimple.

According to a particular embodiment, the gateway comprises: means fordiscovering devices connected to the local area network; means forrepresenting the discovered devices via a user interface; means forenabling a user to define an association of at least one discovereddevice with each private memory space and with respective rights ofaccess to said private memory space; and means for generating at leastone administrator command for updating the access rights managementtable according to the defined association. Thus managing the accessrights is simple.

The invention also relates to a method implemented by a residentialgateway connected to a local area network, the residential gatewayhaving a memory space made available to at least one device connected tothe local area network. The method is such that, said memory spacecomprising at least one private memory space, the residential gatewaycomprising a table for managing rights of access to said private memoryspace or spaces, the residential gateway performs the following steps:receiving commands for access to said memory space and administratorcommands for updating said access rights management table; updating saidaccess rights management table on reception of an administrator commandcoming from a predetermined device implementing an administrator module,and ignoring any administrative command coming from the device notimplementing said administrator module; and ignoring any command foraccess to said private memory space or spaces when said command isreceived coming from a device not identified in said access rightsmanagement table.

The features of the invention mentioned above, as well as others, willemerge more clearly from a reading of the following description of anexample embodiment, said description being given in relation to theaccompanying drawings, among which:

FIG. 1 schematically illustrates a communication network in which thepresent invention may be implemented;

FIG. 2 schematically illustrates an example of hardware architecture ofa residential gateway of the communication network;

FIG. 3 schematically illustrates an algorithm for updating a tablemanaging access rights to at least one private memory space in thecontext of the communication network;

FIG. 4 schematically illustrates an algorithm for declaring, to theresidential gateway, a device administering said access rightsmanagement table;

FIG. 5 schematically illustrates an algorithm for processing commandsreceived by the residential gateway in the context of managing accessesto at least one private memory space;

FIG. 6 schematically illustrates an algorithm for filtering commandsreceived by the residential gateway in the context of managing accessesto at least one private memory space.

FIG. 1 schematically illustrates a Local Area Network LAN 120 in whichthe present invention may be implemented. The local area network 120 isbased on a wired architecture, for example of the IEEE 802.3 type,and/or a wireless architecture, for example of the IEEE 8023.11 type.The local area network 120 comprises a set of devices 110, 111, 112,113. The device 110 is a residential gateway interconnecting the localarea network 120 and a Wide Area Network WAN 121. An example of hardwarearchitecture of the residential gateway 110 is described below inrelation to FIG. 2.

The devices 111 and 112 are devices supplying and/or consuming data,preferentially of the audiovisual type. For example, the device 111 isan STB decoding device having a capability of recording audiovisualdata, as is the case in functions of the PVR or time shifting type, thedevice 112 is a display device of the electronic tablet type, and thedevice 113 is a Personal Computer PC.

The residential gateway 110 comprises a memory space 132 that comprisesat least one private memory space 130, meaning a memory space accessesto which are enabled only from a device preregistered in an accessrights management table. The memory space 132 may comprise at least onepublic memory space 131, meaning a memory space accesses to which doesnot require such prior registration of the device in the access rightsmanagement table. In other words, the access rights management tabledoes not manage any public memory space. The public 131 and private 130memory spaces may be located on separate media or be located on separatepartitionings of the same medium. Hereinafter it is considered, by wayof illustration, that the residential gateway 110 comprises at least oneprivate memory space 130 and at least one public memory space 131.

A server 150 adapted for managing the accesses to said private memoryspace 130 is associated with each private memory space 130. Likewise, aserver 151 adapted for managing accesses to said public memory space 131is associated with each public memory space 131. In other words, theservers 150 and 151 are adapted for processing commands for access tosaid memory spaces 130 and 131 respectively, in read and/or write mode,coming from devices connected to the local area network 120. Unlike theserver 151, the server 150 performs a prior filtering of the commandsaccording to the content of the access rights management table. Eachserver 150 and 151 has a particular identifier, which is allocatedthereto by the residential gateway 110.

In a particular embodiment, each server 150 and 151 is adapted forprocessing the commands in accordance with a data exchange protocol atthe link layer level of the OSI model. The messages exchanged via thelocal area network 120 in the context of accesses to the memory space132 are then link layer messages, also referred to as “level 2messages”. This significantly reduces the latency in transmission andprocessing of these messages, which accelerates the speed of access tothe memory space 132. In a particular embodiment, these link layermessages are in accordance with the AoE protocol. This enablesoff-the-shelf legacy devices supplying and/or consuming data to benefitfrom the present invention, while keeping a simple design of theresidential gateway 110.

The residential gateway 110 further comprises a table 140 for managingrights of access to each private memory space 130. An algorithm forupdating the access rights management table 140 is described below inrelation to FIG. 3.

As detailed hereinafter, in particular in relation to FIGS. 5 and 6,each server 150 responsible for a private memory space 130 filters thecommands to be processed according to the device that generated thecommand and according to the devices and access rights enteredpreviously in the access rights management table 140. The access rightsmanagement table 140 is populated by an administrator module or device141. In FIG. 1, such an administrator module 141 is included in theresidential gateway 110. In a variant embodiment, the administratormodule 141 may be included in another device connected to the local areanetwork 120. The access rights management table 140 may be populated bya plurality of administrator modules 141, provided that theseadministrator modules 141 are known as such to the residential gateway110.

In a particular embodiment, the residential gateway 110 furthercomprises a module 142 managing priority of access to the memory space132. Said module 142 managing priority of access is responsible forsequencing the commands for access to the memory space 132 coming fromthe servers 150 and 151. Managing the priorities of access to the memoryspace 132 is performed thanks to a queue in which the commands comingfrom the servers 150 and 151 are placed. The sequencing of thesecommands is provided according to priority levels allocated to theservers 150 and 151. The sequencing of these commands may further takeinto account the type of device connected to the local area network 120that generated said commands, as well as the type of said commands.

FIG. 2 schematically illustrates an example of hardware architecture ofthe residential gateway 110. The residential gateway 110 then comprises,connected by a communication bus 210: a processor or Central ProcessingUnit CPU 200; a random access memory RAM 201; a read only memory ROM202; at least one storage unit 203, such as a hard disc drive HDD,implementing the public and private memory spaces already mentioned; astorage medium reader, such as an SD (Secure Digital) card reader 204;and a set of interfaces 214 for communicating via the communicationnetworks 120 and 121.

The processor 200 is capable of executing instructions loaded into theRAM 201 from the ROM 210, from an external memory (not shown), from astorage medium, or from a communication network. When the residentialgateway 110 is powered up, the processor 200 is capable of readinginstructions from the RAM 201 and executing them. These instructionsform a computer program causing the implementation, by the processor200, of all or some of the algorithms and steps described in relation tothe residential gateway 110.

Thus all or some of the algorithms and steps described in relation tothe residential gateway 110 may be implemented in software form throughthe execution of a set of instructions by a programmable machine, suchas a Digital Signal Processor DSP or a microcontroller. All or some ofthe algorithms and steps described in relation to the residentialgateway 110 may also be implemented in hardware form by a machine or adedicated component, such as an Field-Programmable Gate Array FPGA or anApplication-Specific Integrated Circuit ASIC.

FIG. 3 schematically illustrates an algorithm for updating the accessrights management table 140.

In a step 301, the administrator module 141 obtains a list ofidentifiers of the devices connected to the local area network 120 andpreferentially the type of these devices. For example, this list resultsfrom a discovery phase according to the Simple Service DiscoveryProtocol SSDP, as implemented in the context of the Universal Plug andPlay UPnP standard.

In a following step 302, the administrator module 141 provides adisplay, via a Graphical User Interface GUI, of representations of thedevices connected to the local area network 120. The display enables auser to select a device from those connected to the local area network120 and to define rights of access, in read and/or write mode, to atleast one private memory space 130. In a particular embodiment, theadministrator module 141 also provides a display of a representation ofeach private memory space 130 created in the residential gateway 110,and enables a user to request that a new private memory space 130 becreated within the residential gateway 110. This enables associating adevice among those connected to the local area network 120 with aprivate memory space and defining the access rights thereof. Informationallowing this representation of each new private memory space 130 may berequested by the administrator module 142 to the residential gateway110.

Such a graphical interface GUI also enables the user to delete orredefine rights of access to each private memory space 130.

In a variant embodiment, the administrator module 141 negotiates, withthe devices connected to the local area network 120, the rights ofaccess to each private memory space 130. Each of these devices mayinclude a set of specific instructions for this negotiation, such as forexample an application in the case where said device is a tablet orsmartphone.

In another variant embodiment, the administrator module 141 uses apre-established definition of the rights of access to each privatememory space.

In a following step 303, the administrator module 141 receivesinformation representing a selection made by the user of a device amongthose connected to the local area network 120 and informationrepresenting access rights associated with said selected device. In theparticular embodiment mentioned above in relation to the step 302, theadministrator module 141 also receives information representing aprivate memory space to which said access rights relate, in particularwhen there may be ambiguity concerning the relevant private memoryspace. The administrator module 141 then transmits to the residentialgateway 110 an administrator command requesting that the residentialgateway 110 updates the access rights management table 140 with saidinformation representing the selected device, the concerned privatememory space (if this is not implicit) and access rights granted to saidselected device with regard to said private memory space.

In the embodiment in FIG. 1 where the administrator module 141 isincorporated in the residential gateway 110, the administrator module141 does not exchange information with the residential gateway 110 viathe local area network 120 and acts directly on the access rightsmanagement table 140.

In a following step 304, the residential gateway 110 updates the accessrights management table 140 according to the association informationsupplied by the administrator module 141 at the step 303.

Preferentially, in order to allow accesses to the private memory spacesin read and/or write mode at reduced latency, a data exchange protocolat the link layer of the OSI (Open Systems Interconnection) model isimplemented, in this case, the MAC (Medium Access Control) addresses areused to identify the devices in the access rights managements table 140.

So as to ensure that only the administrator module 141 is in a positionto request updates to the access rights management table 140, it ispossible to write in non-volatile memory of the residential gateway 110an identifier of the device implementing the administrator module 141,for example at the time of manufacturing of the residential gateway 110.The device implementing the administrator module 141 and the residentialgateway 110 are then hard coupled.

In a preferred embodiment, the residential gateway 110 integrates theadministrator module 141.

Methods for authenticating the device implementing the administratormodule 141 with the residential gateway 110 may also be implemented toensure in a more flexible manner that only the administrator module 141is in a position to request updates to the access rights managementtable 140.

According to yet another variant, a pairing mechanism may beimplemented, as described below in relation to FIG. 4.

FIG. 4 schematically illustrates an algorithm for declaring, to theresidential gateway 110, a device implementing the administrator module141 in the local area network 120.

In a step 401, the residential gateway 110 activates a pairing phase.The step 401 may be triggered following a predefined event, such as forexample the detection of a pressing on a dedicated button of a controlpanel (physical, or virtual via a graphical interface GUI) of theresidential gateway 110. The pairing phase may be activated for apredefined period or until a device has succeeded in pairing with theresidential gateway 110, or until the residential gateway 110 detectsanother predefined event, such as for example a new detection ofpressing on said dedicated button.

In a following step 402, the residential gateway 110 receives a pairingrequest, coming from a device connected to the local area network 120.The sending of this pairing request by said device may be triggeredfollowing a predefined event, such as for example the detection ofpressing on a dedicated button of a control panel (physical, or virtualvia a graphical interface GUI) of said device. In other words, the user,after having pressed on the residential gateway 110 on a first buttondedicated to pairing, presses on the device implementing theadministrator module 141 on a second button dedicated to pairing.

In a following step 403, the residential gateway 110 obtains, from thereceived pairing request, an identifier of the device that sent thepairing request.

In a following step 404, the residential gateway 110 updates an internalregister in which an identifier of the device implementing theadministrator module 141 is stored. The pairing phase is then ended.Only the device the identifier of which is stored in the register isthen allowed to request updates to the table 140 managing rights ofaccess to the private memory space or spaces.

FIG. 5 schematically illustrates an algorithm for processing commandsreceived by the residential gateway 110 in the context of managingaccesses to the memory space 132.

In a step 501, the residential gateway 110 initialises at least oneserver 150 adapted for managing accesses to at least one respectiveprivate memory space 130 and at least one server 151 adapted formanaging accesses to at least one respective public memory space 131.

In a following step 502, the residential gateway 110 activates afiltering of commands received from devices connected to the local areanetwork 120 and relating to accesses to at least one private memoryspace 130. Such a filtering is performed, as described below in relationto FIG. 6, by each server 150 managing accesses to the correspondingprivate memory space 130.

In a following step 503, the residential gateway 110 broadcasts, via thelocal area network 120, at least one message describing theconfiguration of each server 150 managing access to a private memoryspace 130, so as to signify to the devices connected to the local areanetwork 120 that said server 150 is ready to accept commands Eachmessage describing the configuration of a server 150 comprises anidentification of the private memory space 130 managed by said server150, for example by providing an indication of memory sectorsconstituting said private memory space 130. In addition, the residentialgateway 110 broadcasts, via the local area network 120, at least onemessage describing the configuration of each server 151 managing accessto a public memory space 131, so as to signify to the devices connectedto the local area network 120 that said server 151 is ready to acceptcommands Each message describing the configuration of a server 151comprises an indication of the public memory space 131 managed by saidserver 151, for example by providing an indication of memory sectorsconstituting said public memory space 131.

In the particular embodiment based on the AoE protocol, such messagesare of the “Query Config Information Response” type.

In a following step 504, the residential gateway 110 checks whether atleast one command for access to the memory space 132 is awaitingprocessing in the queue already mentioned. The commands are placed inthe queue by the servers 150 and 151. If an access command is waiting inthe queue, a step 505 is performed; otherwise the step 504 is repeated.

In the step 505, the residential gateway 110 retrieves from the queue acommand to read from one memory space 130 or 131, or to write in onememory space 130 or 131, which is awaiting processing. Then theresidential gateway 110 processes the retrieved command, meaningperforms the write operation in the concerned memory space or the readoperation in the concerned memory space. Each command being associatedin the queue with an identifier of the server 150 or 151 that placed thecommand in the queue, the residential gateway 110 is able to provide aresult of the write or read operation to the concerned server 150 or151.

In a particular embodiment, each command placed in the queue isassociated with an indication of priority. In this case, the residentialgateway 110 processes first the top priority commands in the queue and,when several commands are of top priority, the residential gateway 110processes first the oldest top priority command in the queue. It is thenpossible to give higher priority to the accesses to the private memoryspaces 150 compared with the accesses to the public memory spaces 151.

FIG. 6 schematically illustrates an algorithm for filtering commandsreceived by the residential gateway 110 in the context of managingaccesses to the memory space 132.

In a step 601, the residential gateway 110 receives a command for accessto the memory space 132.

In a step 602, the residential gateway 110 determines the type of thereceived command. If the command is an administrator command, meaning acommand issuing from the device implementing the administrator module141, a step 603 is performed; otherwise, if the command concerns apublic memory space 131, the residential gateway 110 shall supply thecommand, for processing, to the concerned server 151 and, if the commandconcerns a private memory space 130, the residential gateway 110 shallsupply the command, for processing, to the concerned server 150. Eachwrite or read command comprises an indication of the concerned memoryspace 130 or 131 or an indication of a concerned portion of the memoryspace 130 or 131. In the particular embodiment already mentioned basedon the AoE protocol, the write or read commands are of the “Issue ATACommand” type, in which the devices that sent said commands indicatewhich memory sectors are concerned. In addition, as described below,commands of the “MAC Mask List” type are accepted with regard to thepublic memory spaces 131, but not with regard to the private memoryspaces 130. Indeed, so as not to disclose the list of devices having theright of access to a private memory space 130 nor to enable writing tosuch a list by clients in accordance with the AoE protocol, the server150 in charge of said private memory space 130 ignores this type ofcommand.

Thus, in a step 606, the concerned server analyses the received commandin order to determine whether the command may be accepted by theresidential gateway 110.

When the command is a command for access to a public memory space 131and is consequently processed by one server 151, said server 151 checksthe integrity of the command received and, in the case of a positivecheck, places the command in the queue in a step 607. When the commandplaced in the queue is processed by the residential gateway 110 at thestep 505, the server 151 supplies a response to the device that sent thecommand, an identifier of said device being contained in the messagethat transported said command via the local area network 120. Thus, whenthe command is a write command, the server 151 generates, in response tosaid command, a message representing the failure or success of theassociated write operation in the concerned public memory space 131;then the algorithm is ended. In the case where the command was receivedcorrupted or when the received command comprises an inappropriate fieldor parameter, in a step 608, the server 151 generates in response tosaid command a message representing an error in the received command;then the algorithm is ended.

When the command is a command of the “MAC Mask List” type concerning apublic memory space 131, the residential gateway 110 passes the commandto the concerned server 151, which processes it in accordance with theAoE protocol.

When the command is a command for access to a private memory space 130and is consequently processed by one server 150, said server 150 checksthe integrity of the command received and, in the case of positivecheck, checks whether the device that sent the command is authorised toaccess said private memory space 130. To do this, the server 150searches the access rights management table 140 and checks whether thedevice that sent the command is identified in said table 140 and whetherthe corresponding access rights allow performing the operationrequested. When the device that sent the command is identified in theaccess rights management table 140 and the command received is inagreement with the access rights that are associated therewith for saidprivate memory space 130, then the server 150 places the command in thequeue in the step 607. When the command placed in the queue is processedby the residential gateway 110 at the step 505, the server 150 suppliesa response to the device that sent the command, an identifier of saiddevice being contained in the message that transported said command viathe local area network 120. Thus, when the command is a write command,the server 150 generates in response to said command a messagerepresenting the failure or success of the associated write operation inthe concerned private memory space 130; then the algorithm is ended. Inthe case where the command was received corrupted or when the receivedcommand comprises an inappropriate field or parameter, or when thecommand is not in agreement with the access rights defined in the accessrights management table 140, in a step 608, the server 150 generates inresponse to said command a message representing an error in the receivedcommand; then the algorithm is ended.

When the command is a command of the “MAC Mask List” type concerning aprivate memory space 130 and this command is not an administratorcommand, the residential gateway 110 ignores said command.

When one server 150 or 151 places a command in the queue, said server150 or 151 associates with said command the identifier of said server150 or 151, in order to enable the residential gateway 110 subsequentlyto make the link between each processed command and the concerned server150 or 151.

As already mentioned, each command in a queue may be associated with apriority level. Each command is then placed in the queue according tothe priority level associated with the server supplying said command.

In the step 603, the residential gateway 110 processes the receivedadministrator command. The command is therefore a command coming fromthe device implementing the administrator module 141. In the particularembodiment according to the AoE protocol, the command is of the “MACMask List” type. The command may concern the addenda in the table 140,vis-à-vis a private memory space 130, of a device of the local areanetwork 120 and access rights associated with this device vis-à-vis saidprivate memory space 130. The command may concern modification, in thetable 140, of the access rights of a device of the local area network120 vis-à-vis a private memory space 130. The command may concerndeletion, from the table 140, of the access rights of a device of thelocal area network 120 vis-à-vis a private memory space 130. Thealgorithm is then ended.

The invention claimed is:
 1. A residential gateway, the residentialgateway having a memory space made available to at least one deviceconnected to a local area network to which is connected the residentialgateway, wherein, said memory space comprising at least one privatememory space, the residential gateway comprises a table managing rightsof access of devices to the at least one private memory space, and theresidential gateway is configured for: receiving commands for access tosaid memory space and administrator commands for updating said tablemanaging rights of access; updating said table managing rights ofaccess, on receipt of an administrator command coming from apredetermined device implementing an administrator module, and ignoringany administrator command coming from a device, different from thepredetermined device, not implementing said administrator module; andignoring any command for access to the at least one private memoryspace, when said command is received from a device different from thepredetermined device and not identified in said table managing rights ofaccess, and the residential gateway comprises a server for each of aplurality of private memory spaces, each of the servers filtering andprocessing the commands for access to the respective private memoryspace, and the residential gateway broadcasts a message describing aconfiguration of each of the servers, said message including adescription of the private memory space managed by each of the servers.2. The residential gateway according to claim 1, wherein the residentialgateway is configured for receiving, via the local area network, saidcommands for access to said memory space in the form of link layermessages.
 3. The residential gateway according to claim 2, wherein theresidential gateway is configured for receiving, via the local areanetwork, said commands for access to said memory space in the form ofmessages in accordance with the AoE protocol.
 4. The residential gatewayaccording to claim 3, wherein residential gateway is configured forignoring any command of the “MAC Mask List” type of the protocol AoEconcerning said private memory space or spaces.
 5. The residentialgateway according to claim 1, wherein, the memory space furthercomprising at least one public memory space not taken into account bythe table managing rights of access, the residential gateway comprises aserver for the public memory space, the residential gateway comprises aqueue in which the server for each of the private memory spaces and theserver for the public memory space places commands for access to therespective private or public memory space to be executed.
 6. Theresidential gateway according to claim 5, wherein the server for each ofthe private memory spaces and the server for the public memory space areassociated with a priority level and each command for access to a memoryspace is placed in the queue according to the priority level associatedwith the server for each of the private memory spaces and the server forthe public memory space supplying said command to be executed.
 7. Theresidential gateway according to claim 1, wherein, when the residentialgateway is not the device implementing the administrator module, theresidential gateway is configured for pairing the residential gatewaywith the device implementing the administrator module.
 8. Theresidential gateway according to claim 1, wherein the residentialgateway is configured for: discovering devices connected to the localarea network; representing the discovered devices via a user interface;enabling a user to define an association of at least one discovereddevice with a private memory space and with respective rights of accessto the private memory space; and generating at least one administratorcommand for updating the table managing rights of access according tothe defined association.
 9. A method implemented by a residentialgateway connected to a local area network, the residential gatewayhaving a memory space made available to at least one device connected tothe local area network, wherein, said memory space comprising at leastone private memory space, the residential gateway comprising a table formanaging rights of access of devices to the at least one private memoryspace, the residential gateway performs: receiving commands for accessto the at least one private memory space and administrator commands forupdating said table for managing rights of access; updating said tablefor managing rights of access on reception of an administrator commandcoming from a predetermined device implementing an administrator module,and ignoring any administrative command coming from a device, differentfrom the predetermined device, not implementing said administratormodule; and ignoring any command for access to the at least one privatememory space of the memory space when said command is received from adevice, different from the predetermined device, not identified in saidtable for managing rights of access, wherein the residential gatewaycomprises a server for each of a plurality of private memory spaces,each server filtering and processing the commands for access to therespective private memory space, and the residential gateway broadcastsa me s sage describing a configuration of each server, said messageincluding a description of the private memory space managed by each ofthe servers.
 10. A non-transitory information storage medium storing acomputer program comprising code instructions causing implementation, bya residential gateway processor, of the method according to claim 9 whensaid code instructions are read and executed by the residential gatewayprocessor.